Release 10.1A: OpenEdge Application Server:
Administration

NSCONFIG

Displays the property settings associated with a NameServer configuration and checks that the syntax and values are valid. The NSCONFIG utility runs locally on the machine where the AdminService is running. The utility does not run across the network.

Syntax

Operating system	Syntax
Windows	nsconfig [ [ [ -name name-server ] [ -propfile path-to-properties-file ] [ -validate ] ] | -help ]

-name name-server

Specifies which existing NameServer configuration to examine. The name must match the name of an existing NameServer configuration in the specified properties file. If you do not specify a NameServer, the NSCONFIG utility analyzes all NameServer configurations defined in the properties file specified by the -propfile parameter.

-propfile path-to-properties-file

Specifies a filename or pathname to a file that contains the property settings to be validated, for example, test.properties. If a filename or pathname is not specified, it defaults to the installation version of the ubroker.properties file, such as:

install-path\properties\ubroker.properties in Windows.
install-path/properties/ubroker.properties on UNIX.

-validate

Checks the syntax and values of property settings defined in the specified properties file.

-help

Displays command-line help.

Notes

Never needed if you always use the Progress Explorer GUI.
A single NameServer can simultaneously support all of the AppServer, WebSpeed, and DataServer products using Progress Explorer.

Examples

Table B–3 shows several examples that use the NSCONFIG command. Assume the NameServer is NS1.

Table B–3: NSCONFIG command examples 

Task	Command
View a NameServer configuration.	nsconfig -name NS1
View a NameServer configuration defined within a different property file.	nsconfig -name NS1 -propfile g:\other.properties -validate

For information on managing a NameServer using the NSCONFIG utility, see OpenEdge Getting Started: Installation and Configuration .